I can't understand what the import problem is exactly, it seems that the script starts to import the .obj file correctly until a certain point but I can't identify it.
yeah it would be quicker and easier to post the blend files, but I don't have web space to do it myself, and there may be some copyright problems.

Python is a programming language, the scripts we use in Blender are written in python. The python console is the DOS-like windows which spawns each time you launch Blender. This console tells some informations about Blender when it executes python scripts, so if there's a python error, that console tells it to you.

what does the python console say exactly?

OK I will work on a stable version, but it will make basic notices in game to release it as soon as possible.
I will probably use the future button system in LFS.

Finally fuel management in LFS will be possible :banana:

Yes it uses Outgauge and Insim, there's possibility to receive outgauge packets via Insim but it's too hard to manage for me, and chances to miss packets would be increased.

For the pit reminder & co, these are planned, plus other features to help pit stop managing.

There's no distance calculation. The app gather the fuel level in real time (a float type value, ultra precision :Eyecrazy and performs a simple subtraction.

there's a screenshot:

MOUARF

|_ () |_

Quote :

Kyoto = Tokyo?

Quote :

BOB SMITH <-> SHIT BOMB

the funniest thread of the forum ever...

partypope: have you set Yafray up correctly? do you have a camera in your scene?

black vampire: good render and good settings for the shadows; rims seem to be hard worked

Now my last test render:



Rendered with Blender's internal renderer only. I Just worked the materials, added a sun lamp, used a HDR image for the sky and its light for ambient occlusion. The only things that are annoying me are the glasses. They have a nice smoked effect but I don't wanted it and didn't not managed yet to transmit the light in the cockpit correctly. I didn't have this problem with Yafray however.

I think I'll continue to work with Blender's renderer only because it's a lot easier and quicker for production. Yafray is slow and hard to setup, Indigo is better but painfully the slowest, hard to use and we must entirely redefine materials for it without previewing the settings.

EDIT:
glass tweaked:


Turned off 'raytraced' for glass material to let the light enter the cockpit, and switched to 'ztransparent' instead of 'ray transparent', to see the sky through the windows. Then the mirror effect and opacity have been increased to keep the realistic effect of glass. There's still too much noise...

Last edited by Bogey Jammer, Sun, 12 Aug 2007 11:30. Reason : new screenshot

Wow the report proves the work needed for the analyzer is enormous :Eyecrazy: I will better savour this.
The comparison with other analysis softwares tells us that this analyzer is the only one which is free and so versatile, it's a true pearl

All the informations are well presented in this report, the routine diagrams are good idea.

Very precious document

Just tested it, it seems to work but..

what is it? what's the goal? why is it called easteregg?

there will be a GUI, but simple and without artefacts

I don't understand what you mean, but the app uses Insim and Outgauge.

Quote from wheel4hummer :

Just make a Win32 build of it using py2exe.

I didn't know it is possible, great !

Quote :

Yes, the setup guide will continue to be a seperate document. The setup guide would not need to updated for every little change in the program, whereas the manual probably would.

mmh, I didn't explain correctly, I just meant one sentence like "refer to the advanced setup guide for precious information" in the analyzer manual.

There are lot of good ideas in the improvement list :hyper:

Quote from Gentlefoot :

So I guess it flashed up the fuel burnt at the end of each lap yes?

Currently yes. But I want to add more features, such as logging, strategy assistant and more notifications.

simply asking opinions

Hi all :jester:

I've programmed a rudimentary app to notify me in game how much fuel I burnt in a lap.
For me this tool is extremely useful and has great potential, enough to wonder if it would be the same for the community.

I theoretically attached a poll with this thread but please read this before to vote:

I'm not an expert programmer, I program it with Python only (what Python is: http://www.python.org/), so the user must install Python interpreter, so the app is not stand alone (it also spawns a console window). In brief it's not an app with a cool interface (and probably not very well coded)
The app is still at a prehistoric stage, a public release means serious improvements, more features, and of course lot of time to make it.


Please let me know what do you think about it

OK I've just read the manual, it's exhaustive to learn how to use the analyzer but not how to create setups with it; however I think it's not the goal anyway..

Since this excellent tool could be used for other games and some car applications, I would like to know the LFS physics calculation limitations, like the linear undertray ground effect, aero calculation, and other physical interactions that are not calculated in LFS but present in the reality. And also the current analyzer calculations which are not yet coherent with LFS (like the suspension geometry as mentioned above)

A formula summary may be useful to know where the magic results come from, and for everyone car engineering education :nerd:

I think some technical words should be explained, a fresh noob may not know what "unsprung mass" is, and may be confused with the different meanings of "acceleration". The analyzer's manual should also invite the noob to study your excellent setup guide.

About your big list of improvement, what are they? :yummy:

another question in that style:
Spring forces calculation are made without motion ratio, isn't it? Are the springs stricly vertically modeled in the analyser?

The new default sounds are awesome!!
GREAT improvement for immersion

Both

Quote from wsinda :

Um, what do you use histogram plots for? I've seen them in MoTec, but couldn't see how they can be useful.

I use them to watch data related to suspension. They can be used for other interesting things.

Quote from windsa :

XY plots are already on my list. Or in any case, a traction circle graph is on it. That seems to me the most useful example of an XY plot. (BTW, F1PerfView can do them, but maybe they're too limited for your taste.)

F1perfview's XY plots suck, even if it's my taste or not. MoTec-style colored dots are so far better for lisiblity.

I've just tested this program and it has a great potential. Clearly simpler to use than F1perfview.
Since I like MoTec's interface, I would like to see histogram and XY plotting features, what F1perview is cruelly lacking of.

nihil:
an example for a 6 lap race
run replay once, output the 1st, 3rd, 5th laps, fast forward between these laps (LFS can't output two consecutive lap in one replay run)
Then replay only one more time to output in the same way the 2nd, 4th and 6th laps.
You need to restart only one time the replay whatever the lap number is 5, 25 or 100, not for each lap (as I think I've understood)

Future releases sound better than I thought what a great program

Quote :

Car pitch didn't really affect aero distribution until I coded dynamic wing angles the other night, so I'm not sure what you're seeing there. It should be very small, whereas now it should be quite pronounced for cars with downforce

It's the FXR. The slider range can be exaggerated, but we can see that it affects the forces.

Quote :

Undertray is not affected by pitch or ground clearance in LFS, thus I have no data with which to build my own model. I will it add when LFS does.

I didn't know that ground effect in LFS works like this. It's quite a disappointment, it's so sensitive in the reality.. But your program is coherent with LFS, that's most important.

The program works perfectly with me and is so useful

now my suggestions:

• ability to watch acceleration time in a custom speed range.
  
• zoom-in graphs with values on axis for precision reading, and keys.
  
• more help for ackermann setup, what is the optimal corner radius the current ackermann setting set up?
  
• a global over/understeer diagram which takes in account all elements
  
• what do the dots represent in the springs tab's bottom graph?

and the questions:

1. I've noticed that the springs stiffness influences the aero force distribution. May I conclude this distribution takes in account the car pitch?
   
2. Is it normal that undertray's ground effect forces are not affected by car pitch and ride height? (not implemented yet I think?)

Last edited by Bogey Jammer, Mon, 19 Mar 2007 14:59. Reason : orthograph